home *** CD-ROM | disk | FTP | other *** search
- % Line that begin with a "%" are comment lines and do not affect the
- % program in any manner. *ALL* settings entered in this configuration
- % file CAN BE EDITED when running the program. These represent the settings
- % you would use most often. Thus, when in the program, you will only
- % have to press <ENTER> on the various fields, unless you wish to change
- % one of the settings.
-
- % CDROM= represents your CD-ROM Drive. If you have a single drive CD-ROM
- % then enter the letter here. If you have a multi-disk CD-ROM,
- % then enter the drive of the CD you wish to process.
- % Example setting: CDROM=G
-
- CDROM=G
-
- % TYPE= represents the Type of file area and the type of Date Listing
- % needed for this CD-ROM. Please see the Maximus 3.0 documents
- % for more information on this setting. For most CD-ROMs, the
- % recommended setting would be "CD Datelist," which means the
- % file area is a CD-ROM and the FILE####.BBS listing contains
- % the DATE and SIZE of the files.
- % Example setting: TYPE=CD DATELIST
-
- TYPE=CD DATELIST
-
- % STORAGE= represents the subdirectory you wish the program to place the
- % converted/copied FILES.BBS. Each FILES.BBS will be renamed
- % FILE####.BBS, where #### represents the AREA NUMBER the program
- % assigned. When searching for FILES.BBS (or it's equivalent)
- % in subdirectories, the program begins in the HOME DIRECTORY of
- % the CD and searches all parent and child subdirectories below
- % the home subdirectory. Well, not all, but it will go NINE
- % subdirectories deep. That should be good enough for almost
- % ALL cd's. 8-) Remember, if you re-use STARTAREA number, you
- % will over-write existing FILE####.BBS. Each CD should probably
- % have a unique set of numbers (i.e. the first CD 100's, second
- % CD 200's, etc.), although that is not necessary. Just be sure
- % that they is no overlapping of numbers. This, most likely, will
- % remain the same from CD to CD. The program will try to check to
- % make sure this is a valid subdirectory and already exists. If
- % you do wish to use overlapping file area numbers (STARTAREA),
- % make sure each CD has it's own STORAGE subdirectory.
- % Example setting: STORAGE=F:\MAX\CDROMS
-
- STORAGE=C:\MAX\CDROMS
-
- %UPLOAD= represents the subdirectory you wish Maximus to place ALL uploaded
- % files when the BBS user is in an area on the CD-ROM. This, mostly
- % likely, will remain the same from CD to CD.
- % Example setting: UPLOAD=F:\MAX\FILE\UNCHECK
-
- UPLOAD=C:\MAX\FILE\UNCHECK
-
- %ACCESS= represents Max's Security Level (i.e. TRANSIENT, DEMOTED, NORMAL,
- % etc.) The program WILL check for proper Max 3.0 security levels.
- % You can add keys or whatever to the level (i.e. NORMAL/C). While
- % you can change this, it probably will remain the same from CD to
- % CD too.
- % Example setting: ACCESS=NORMAL
-
- ACCESS=NORMAL
-
- %FILESBBS= represents the name of the file in each subdirectory that contains
- % the listing and descriptions of the files in that subdirectory.
- % With most recent CDs, that name is probably "FILES.BBS." However,
- % should that not be the case, you may enter the name that does
- % contain the listing in the program or here on this line. For
- % instance, "DIR.TXT" might be a name. Even worse, "DIR##.TXT"
- % where "##" represents the subdirectory number. For those types
- % of names, you may enter "DIR*.TXT" or "DIR*" for "DIR##" files.
- % The program will attempt to gather the proper information. One
- % problem would be files with names like "DIREXE.ZIP" getting
- % included in the process. This is one area I still need to work
- % on and correct. Example setting: FILESBBS=FILES.BBS
-
- FILESBBS=FILES.BBS
-
- %CTLFILE= represents the FILEAREA.CTL file and subdirectory. I DO NOT
- % recommend that you use FILEAREA.CTL. Let's face it, things
- % can happen that may mess up the file selected. What I would
- % recommend is that you give EACH CD a UNIQUE .CTL file name.
- % Thus, "So Much Garbage 5" would have a name of "SMG5.CTL."
- % While "Dock 6" would have a name of "DOCK6.CTL." Assuming you
- % gave each CD a different STARTAREA number, all you have to do
- % is merge "SMG5.CTL" and "DOCK6.CTL" into your FILEAREA.CTL
- % file with your favority text editor. One drawback to all of
- % this is that you have to edit the DESC line in the FILEAREA.CTL.
- % The program will only put the subdirectory name on that line.
- % However, you can be prompted to enter EACH Subdirectory's
- % Description as the CD is processed. See GETDESCRIPTION.
- % Example setting: CTLFILE=F:\MAX\CTLFILES\SMG5.CTL
-
- CTLFILE=C:\MAX\CTLFILES\NAMEOFCD.CTL
-
- %STARTAREA= represents the FIRST FILE AREA NUMBER you desire for the
- % CD being processed. Give EACH CD a unique starting number
- % and don't overlap any. For instance, you may give "So Much
- % Garbage 5" a starting number of 501. The first subdirectory
- % the program finds with a "FILES.BBS" will be 501. The next
- % will be 502, etc. Give "DOCK 6" a starting number of 601,
- % and you can keep both CDs on-line at the same time or change
- % CDs with just a little editing of the FILEAREA.CTL and then
- % running SILT(p) and FB(p). If you wish to re-use a starting
- % number and all the subsequent area numbers, simply compress
- % all the data files for the CD with the numbers you wish to
- % use. Thus, you can quickly add that CD back to your on-line
- % collection with minimal effort. If you insist on using the
- % same starting number, then give each CD a separate STORAGE
- % subdirectory. See STORAGE.
- % The program will left pad the STARTAREA number with "0"'s so
- % all the FILE####.BBSes will sort correctly in a directory.
- % The File Area Name *will not* be padded with "0"'s. Thus, an
- % area number of 101 will produce "FILE AREA 101" in the CTL
- % file and a "FILE0101.BBS" file in the CDROMS subdirectory.
- % Example setting: STARTAREA=101
-
- STARTAREA=101
-
- %GETDESCRIPTION= represents your desire to be prompted for the File Area
- % Descriptions on-the-fly. If this is set to TRUE, as each
- % subdirectory is discovered on the CD-ROM, a window will
- % pop-up with the control information asking you to enter
- % a description. If you have a list of file areas, you can
- % easily enter the descriptions then and won't have to edit
- % the CTL file again. If you set this setting to TRUE, you
- % will be able to skip certain subdirectories on the CD that
- % you do not want included on your BBS. Pressing <ALT-X>
- % when prompted for a description will skip the subdirectory
- % presented without messing up the File Area numbering.
- % (Valid choices are TRUE or FALSE.)
- % Example setting: GETDESCRIPTION=FALSE
-
- GETDESCRIPTION=TRUE
-
- %MAKEMULTI= represents your desire to take single-line descriptions and
- % turn them into a MULTI-LINED Description. The description
- % may or may not contain dates and sizes for removal or adding.
- % The program will add a "| " at the start of the continuation
- % line, of course, preceeded by the spaces set in the LEFTMARGIN
- % setting (see below). If this setting is TRUE, then the program
- % will set SINGLELINE to FALSE and you will not be able to
- % edit the LINELENGTH setting below. Probably under most
- % normal circumstances, you will want this set to FALSE.
- % Please note that setting this to true on FILES.BBS that are
- % already multi-lined may give unexpected results, although I
- % tried it and it seemed to work properly. Please check the
- % FILES.BBS before setting this to TRUE.
- % (Valid choices are TRUE or FALSE.)
- % Example setting: MAKEMULTI=TRUE
-
- MAKEMULTI=FALSE
-
- %SINGLELINE= represents your desire to take multi-line description files
- % and convert them into a single line for Maximus. The program
- % will truncate the file/description line at the LINELENGTH
- % setting below. If you wish to keep multi-line descriptions,
- % set this option to FALSE. Multi-line description will take the
- % description found in the FILES.BBS file and attempt to format them
- % in a way pleasing to Maximus. The program will leave the begin-
- % ning "|" character on description lines that ARE NOT a file name
- % line OR add it, if needed. This allows Maximus to search the
- % entire description when doing a LOCATE. The "|" is NOT displayed
- % doing a LOCATE, but IS displayed when doing a FILES Listing.
- % I'm not exactly sure why. The program will pad the descriptions
- % with extra spaces for the left margin as needed. To have single
- % line descriptions, set this option to TRUE. See LEFTMARGIN below.
- % You may have to adjust the FILE MARGIN setting in the MAX.CTL
- % file. I have mine set for 31 and everything lines up properly.
- % Since there are so many different formats to FILES.BBS files,
- % this may not work properly on all CDs. Since I haven't used
- % a DOWNLOAD COUNTER, I'm not sure how they would affect these
- % files. Please note that setting SINGLELINE to FALSE does NOT
- % MAKE multi-line descriptions out of single-line descriptions.
- % Only setting MULTILINE to TRUE will do that. Setting SINGLE-
- % LINE to FALSE assumes that the FILES.BBS is already a multi-
- % line description. (Valid choices are TRUE or FALSE.)
- % Example setting: SINGLELINE=TRUE
-
- SINGLELINE=TRUE
-
- %LINELENGTH= represents the LENGTH you wish for a SINGLE LINE Description.
- % Maximus 3.0 can handle single line descriptions of up to 1024
- % characters. For various reasons, you may wish to limit the
- % length of a single line description to something less than the
- % allowable 1024 character. Any valid integers greater than 35
- % and less than 1025 are acceptable entries. This option is only
- % important if you have set SINGLELINE to TRUE.
- % Example setting: LINELENGTH=512
-
- LINELENGTH=1023
-
- %LEFTMARGIN= represents the number of spaces that should be added before
- % any continuation lines of a multi-line description. This
- % option is only available *IF* you have set SINGLELINE set to
- % FALSE or MULTILINE set to TRUE. The number entered here will
- % translate to spaces BEFORE the "|" is added to a description
- % continuation line. Valid entries are between 1 and 55.
- % Example setting: LEFTMARGIN=31
-
- LEFTMARGIN=31
-
- %REMOVEDATE= represents the option to remove the FILE SIZE and DATE
- % information from the description files. Since some CD's
- % FILES.BBS files have this information and others don't, you
- % may have to remove or add this information depending upon your
- % preferences. If you wish to remove the SIZE/DATE information,
- % set this option to TRUE. However, if you wish to keep the
- % information in the FILE####.BBS, then set this option to FALSE.
- % You must check each CD's FILES.BBS to determine the proper
- % setting. SCDMAX will remove the size and date information
- % starting with the column number you entered for STARTCOLUMN
- % and end with the number entered for the ENDCOLUMN settings,
- % assuming you have REMOVEDATE=TRUE. After removing the size
- % and date information, SCDMAX will format the line according
- % to the setting for SINGLELINE and MULTILINE above. Typical
- % settings for these are:
- % REMOVEDATE=TRUE
- % STARTCOLUMN=14
- % ENDCOLUMN=31
- % If REOVEDATE=FALSE, the STARTCOLUMN and ENDCOLUMN have no
- % effect on the program. (Valid choices are TRUE or FALSE.)
-
- REMOVEDATE=FALSE
- STARTCOLUMN=14
- ENDCOLUMN=31
-
- %GETDATE= represents the option of forcing the program to retrieve and
- % add the SIZE and DATE for each file in the FILES.BBS listing.
- % Since some CD's include this information in the listings, while
- % others don't, you must check the actual listings for each CD.
- % The program will put the SIZE in columns 14 to 21 and the DATE
- % in columns 24 to 31. The actual description for the file will
- % begin in column 34. See REMOVEDATE above.
- % (Valid choices are TRUE or FALSE.)
- % Example setting: GETDATE=TRUE
-
- GETDATE=TRUE
-
- %WARNING: Please note that setting GETDATE to TRUE and REMOVEDATE to TRUE
- % may result in unexpected problems. The program will force one
- % to be FALSE, but you might be able to fool it some how. This
- % warning also applies to MULTILINE and SINGLELINE. Both may
- % be FALSE, but both can not be TRUE and expect the program to
- % be successful.
-